[v2] Decouple server from express and hono - http framework-agnostic MCP server
#1326
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v1includedexpress(andhonoin recent version), forcing the dependency down to users. (expressbeing >1MB along with middleware deps such asexpress-rate-limitetc.).Achieving final & true implementation of #1299
This PR decouples
@modelcontextprotocol/serverfrom HTTP frameworks completely, and introduces two plugin packages@modelcontextprotocol/server-expressand@modelcontextprotocol/server-hono.The plugin packages are optional, and users could choose to use them or to map to the MCP SDK themselves and not using any of these plugins.
However, the
@modelcontextprotocol/serveris completely HTTP framework dependency-free.Some additional changes:
StreamableHTTPServerTransporttoNodeStreamableHTTPServerTransportimport { A, type B}). Preferimport type { B }andimport { A }on separate lines.Motivation and Context
v2
How Has This Been Tested?
Unit tests
Breaking Changes
v2
Types of changes
Checklist
Additional context